Add TypeScript types to element-hiding feature #2016
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Asana Task/Github Issue: https://app.asana.com/1/137249556945/project/72649045549333/task/1211479926220519?focus=true
Description
This integrates the refactored schema types from privacy-configuration into the content-scope-scripts element-hiding feature for better type safety and maintainability.
Testing Steps
Checklist
Please tick all that apply:
Note
Adds JSDoc schema types, type guards, and null-safe defaults to
injected/src/features/element-hiding.js
, tightening rule/value handling and style tag injection.ElementHidingValue
,ElementHidingRule
, domain/config types; annotate functions with these types.'selector' in rule
) before querying DOM or building selectors.rule.values
beforemodify-attr
/modify-style
and type params formodifyAttribute
/modifyStyle
.getFeatureSetting
returns with explicit types and safe defaults forrules
,adLabelStrings
,useStrictHideStyleTag
,hideTimeouts
,unhideTimeouts
,mediaAndFormSelectors
.injectStyleTag
andhideAdNodes
to handle rules withoutselector
.extractTimeoutRules
,applyRules
,expandNonEmptyDomNode
).Written by Cursor Bugbot for commit 9f7d33f. This will update automatically on new commits. Configure here.